Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: update to Angular 19 #200

Merged
merged 1 commit into from
Dec 17, 2024

Conversation

luii
Copy link
Contributor

@luii luii commented Dec 17, 2024

Changes that were applied:

  • bump dependency versions
  • applied migrations from migrations.json
  • remove unused component imports
  • add as unknown to updateOptions to fix a previously working type conversion
  • add skipToken check to normalizeOptions to narrow down typing

PR Checklist

Please check if your PR fulfills the following requirements:

No addidtional changes were made

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: #199

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

There is a type conversion that previously was working in updateOptions, now i added as unknown to it to make it work again. Linting and testing did work out of the box, so no changes were made here. Only building had the error on top and the skipToken check, since now the queryFn has a unique symbol as additional type on it, for that reason i added the check on it to filter out the symbol and return the default options. So maybe it would be good if you can check what i did @NetanelBasal and if everything checks out to your liking

Changes that were applied:

- bump dependency versions
- applied migrations from `migrations.json`
- remove unused component imports
- add `as unknown` to `updateOptions` to fix a previously working
  type conversion
- add `skipToken` check to `normalizeOptions` to narrow down typing
Copy link

stackblitz bot commented Dec 17, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@@ -166,7 +166,7 @@ export function createBaseQuery<
...newOptions,
},
injector,
) as QueryObserverOptions<
) as unknown as QueryObserverOptions<
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@NetanelBasal dont know if this can be changed in a reasonable way, but it complained about an incompatibility on TQueryKey which suddenly was TQueryKey & {} (which is weird since its always a ReadonlyArray<unknown>, and this type only says that it should filter out null and undefined values - atleast this is what & {} does since i last checked)

@NetanelBasal NetanelBasal merged commit f6f79a1 into ngneat:main Dec 17, 2024
1 check passed
@Drunkenpilot
Copy link

Got an issue after installed https://github.com/angular /code@19.0.5

npm warn Could not resolve dependency:
npm warn peer @angular/core@">=16.0.0 <=19.0.4" from @ngneat/query@3.1.0
npm warn node_modules/@ngneat/query
npm warn @ngneat/query@"^3.1.0" from the root project

@Ookamini95
Copy link

Got an issue after installed https://github.com/angular /code@19.0.5

npm warn Could not resolve dependency: npm warn peer @angular/core@">=16.0.0 <=19.0.4" from @ngneat/query@3.1.0 npm warn node_modules/@ngneat/query npm warn @ngneat/query@"^3.1.0" from the root project

try downgrading to angular version 19.0.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants